Skip to content

[Snyk] Upgrade xstate from 4.13.0 to 4.14.0#85

Open
snyk-bot wants to merge 1 commit intomasterfrom
snyk-upgrade-f6b508d9391dc7a406d747fc52f10346
Open

[Snyk] Upgrade xstate from 4.13.0 to 4.14.0#85
snyk-bot wants to merge 1 commit intomasterfrom
snyk-upgrade-f6b508d9391dc7a406d747fc52f10346

Conversation

@snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade xstate from 4.13.0 to 4.14.0.

merge advice
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2020-11-05.
Release notes
Package name: xstate
  • 4.14.0 - 2020-11-05

    Minor Changes

    • 119db8fb #1577 Thanks @davidkpiano! - Expressions can now be used in the stop() action creator:

      // ...
      actions: stop(context => context.someActor);

    Patch Changes

    • 8c78e120 #1570 Thanks @davidkpiano! - The return type of spawn(machine) will now be Actor<State<TContext, TEvent>, TEvent>, which is a supertype of Interpreter<...>.

    • 602687c2 #1566 Thanks @davidkpiano! - Exit actions will now be properly called when an invoked machine reaches its final state. See #1109 for more details.

    • 6e44d02a #1553 Thanks @davidkpiano! - The state.children property now properly shows all spawned and invoked actors. See #795 for more details.

    • 72b0880e #1504 Thanks @Andarist! - Added status property on the Interpreter - this can be used to differentiate not started, running and stopped interpreters. This property is best compared to values on the new InterpreterStatus export.

  • 4.13.0 - 2020-08-27

    Minor Changes

    • f51614df #1409 Thanks @jirutka! - Fix type ExtractStateValue so that it generates a type actually describing a State.value

    Patch Changes

    • b1684ead #1402 Thanks @Andarist! - Improved TypeScript type-checking performance a little bit by using distributive conditional type within TransitionsConfigArray declarations instead of a mapped type. Kudos to @amcasey, some discussion around this can be found here

    • ad3026d4 #1407 Thanks @tomenden! - Fixed an issue with not being able to run XState in Web Workers due to assuming that window or global object is available in the executing environment, but none of those are actually available in the Web Workers context.

    • 4e949ec8 #1401 Thanks @Andarist! - Fixed an issue with spawned actors being spawned multiple times when they got spawned in an initial state of a child machine that is invoked in the initial state of a parent machine.

      Illustrating example for curious readers.
      const child = createMachine({
        initial: 'bar',
        context: {},
        states: {
          bar: {
            entry: assign({
              promise: () => {
                return spawn(() => Promise.resolve('answer'));
              }
            })
          }
        }
      });
      

      const parent = createMachine({
      initial: 'foo',
      states: {
      foo: {
      invoke: {
      src: child,
      onDone: 'end'
      }
      },
      end: { type: 'final' }
      }
      });

      interpret(parent).start();

from xstate GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant